- This is a very important topic,
mainly when you start a job.
So let's say that through your journey
you went to the interview, not you start a job.
Although you kind of have an idea
of what you need to do based on the job application,
and in the responsibilities that were posted,
you may realize that there is actually much more to do it.
And on this conversation that you are going to have
with your manager, you need to really understand
and ask for clarity on things that need to be done.
It's very important that on this initial meeting
with your new manager, you say, clearly,
"okay, I understand the job role, but I want to have clarity
on my responsibilities and as well as my expectation.
What do you expect from me?"
Understand what the expectation for you
according to the job level.
And already have a conversation to say,
"I really am looking forward to exceed those expectations."
Because in reality
you always want to exceed those expectations.
You are the professional and you are your own brand.
You have to preserve your name.
So if they say, here is 100%,
always aiming for 120.
Because even if you fail to deliver 120,
you most likely will deliver 100.
Sometimes when you aim for 100, you may get to 90%.
So that's why it's always good to know,
alright, what do you consider above and beyond?
What do you consider above the expectation?
That's where you want to go,
or that's where you at least want to have clarity about.
Review the list of tasks for which you are responsible for.
What are the things that I need to do on a daily basis?
Of course, this is just the beginning.
Understanding those things.
Of course, with time you're gonna have creativity
to suggest new things.
That's when you're gonna start to have a,
even a bigger impact is by thinking through the options
and the processes that can be improved over time.
Map your responsibilities according to what was delivered
to you from your manager.
For example, let's say your manager told you
your main responsibility is to automate
the vulnerability assessment process
for all production servers located
in the financial sector subnet.
It's very compiled, it's very specific.
You know exactly what you need to achieve.
So you have to decompose this whole thing here.
And I'm using this diagram because the idea is really
that you look at each term and see,
are you familiar with those terms?
Because you, remember, you new in this field.
Do you know what really automation means?
If there is any particular language that you have to master,
or at least that you have to research more about.
What about vulnerability assessment?
What is the vulnerability management solution
that the company use?
In this case if they use Qualys,
and maybe you are not familiar with Qualys,
which means that you have to do some ramp up
to learn more about this technology.
What about the production service?
Which operating system they have?
You may reflect and conclude that,
"well if it is Windows, I really have a good level
of understanding of Windows, maybe 300 level of Windows.
But if it is Linux, I'm only 100."
So you see, you start looking at all the terms
and the things that are connected with those terms,
and realize that,
"hey, there are many things here that I've never done,
or that I need to learn more."
And you start to mapping those things.
That's why it's so important to create this mapping.
And then you start planning your next steps.
Okay, now that I already map everything,
that I already know my responsibilities,
let me do this self-assessment to understand
what do I need to do to get there,
and to implement those things.
So you're gonna start working on a ramp-up project for you.
And this ramp-up projects, for example,
it needs to include the time that you're gonna take
to learn the technology, the PoC,
the proof of concept that you are going to do
because you want to create this automation
and deploy in a lab environment before you go to production.
Then you do the implementation and post-deployment.
So we are talking about here, 35 days in this plan.
It's really up to you.
This is just an example of what you could do
to break down and include your own ramp-up,
your learning experience in the first 15 days,
and then the PoC before you go to the implementation
and post-deployment learnings.
Because the post-deployment is very important
to understand what did go well,
what can be improved for the next time.
You always going to do this post-mortem analysis
to evaluate what went well and what needs to be improved.